What does this PR do?

Updates how probes (readiness, liveness, startup) are handled when defined in container-overrides. Since fields for success/failure threshold, period, and timeout are defaulted by the cluster, we have to make sure they're either set to user-provided values or the defaults to avoid repeatedly reconciling the deployment yaml

What issues does this PR fix or reference?

Closes #1093

Is it tested? How?

To test, you can use the workspace

kind: DevWorkspace
apiVersion: workspace.devfile.io/v1alpha2
metadata:
  name: test-dw
spec:
  started: true
  template:
    attributes:
      controller.devfile.io/storage-type: ephemeral
    components:
      - name: terminal
        container:
          image: quay.io/wto/web-terminal-tooling:next
          memoryLimit: 512Mi
          mountSources: true
          command:
           - "tail"
           - "-f"
           - "/dev/null"
        attributes:
          container-overrides:
            readinessProbe:
              exec:
                command: ["echo", "hello"]
            livenessProbe:
              exec:
                command: ["echo", "hello"]
            startupProbe:
              exec:
                command: ["echo", "hello"]

This workspace should start normally with defaulted fields for the probes.

PR Checklist

• E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)
  • v8-devworkspace-operator-e2e: DevWorkspace e2e test
  • v8-che-happy-path: Happy path for verification integration with Che